Information processing system and management device for managing relocation of data based on a change in the characteristics of the data over time

ABSTRACT

In an information processing system including a computer device, and a storage device storing data used by the computer device, the region in which the data is held is managed in association with a change, over the passage of time in the performance and availability required of the data holding region. The computer device includes a storage device managing unit for managing the storage device which stores data used by the computer device. The storage device managing unit periodically monitors temporal characteristics information, and moves data, if the storage region having functional characteristics corresponding to the temporal characteristics information is different from the storage region to which the data is currently assigned.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of application Ser. No.11/299,829, filed Dec. 13, 2005, now U.S. Pat. No. 7,502,904; which is acontinuation of application Ser. No. 10/828,306, filed Apr. 21, 2004,now U.S. Pat. No. 7,096,336 and is related to and claims priority fromJapanese Patent Application No. 2004-003981, filed on Jan. 9, 2004, theentire disclosure of which is incorporated herein by reference.

BACKGROUND OF THE INVENTION

The present invention relates to an information processing device,comprising a computer device, and a storage device for storing data usedby the computer device, wherein data is relocated between a plurality ofstorage devices in accordance with a change in the characteristics ofthe data with the passage of time.

There are disk array systems which achieve high-speed operation and highreliability by providing a plurality of disk devices in an arrayfashion, in a single two-dimensional storage system for an informationprocessing system. The disk devices have distributed access and areoperated in a parallel fashion, thus providing redundancy for the storeddata.

A disk array system provided with redundancy is assigned various RAIDlevels, from RAID level 1 to level 5, according to the redundancystructure (for example, see the below-listed Non-Patent Reference 1),and data transmitted from a host computer connected to the disk arraysystem is located in a plurality of disk devices, in accordance with theRAID level.

In a disk array system, the logical storage region that is recognizedwhen the system is accessed by a host computer is associated with aphysical storage region indicating an actual storage region in the diskdevice, in such a manner that the host computer is not aware of the factthat the data is stored in a distributed fashion in a plurality of diskdevices.

When constructing a disk array system of this kind, in order to achieveoptimal cost performance, disk devices of differing storage capacitiesand differing characteristics may be used in combination. In a case ofthis kind, desirably, the data transmitted by the host computer andlocated hypothetically in a logical storage region is stored in thephysical storage region provided by the most suitable disk device, onthe basis of indicators relating to access frequency and accesspatterns, and the like.

In a system which combines disk devices of different characteristics,the method used for allocating the data to the physical storage regionprovided by the most suitable disk device involves, for example,technology whereby the data access frequency is monitored and data ismoved to the most suitable physical region on the basis of the accessfrequency (see, for example, the below-listed Patent Reference 1.)

In the technology disclosed in Patent Reference 1, a threshold value isset previously, the frequency of access to the data is monitored, and ifthe access frequency has exceeded the threshold value, then the data ismoved to a physical storage region provided by the disk device operatingat a higher speed. Furthermore, it is also possible to relocate theactual logical storage region itself, wherein the disk array systemmonitors the conditions of the access load to the respective logicalstorage regions from the host computer, and determines the details ofthe relocation in such a manner that the data is optimally located afterrelocation, in accordance with the results of the load monitoring. Whenthe logical storage region has been relocated, the association betweenthe logical storage region and the physical storage region is changed tothe physical storage region after relocation.

Furthermore, there is also technology for performing relocation whereinthe use status of a disk device corresponding to read/write operationsfrom the host computer is gathered, the disk access is predicted fromthe information thus gathered, and the most suitable disk device forlocating the data is determined (see, for example, the below-listedPatent Reference 2).

Moreover, in a document relating to SMI-S (Storage Management InitiativeSpecification) under deliberation by the SNIA (Storage NetworkingIndustry Association), which is a storage industry group, technology fora storage system consisting of a disk array system is described, whereina logical storage region is assigned to a physical storage regionprovided by a disk device, in accordance with previously determined“hints” which indicate the access characteristics for the data (see, forexample, the below-listed Non-Patent Reference 2). The storage systemconforming to SMI-S is equipped with functions for selecting a physicalstorage region on the basis of a “hint” and assigning a logical storageregion to the same.

(Non-Reference Patent 1) D. Patterson, G. Gibson and R. H. Kartz, “ACase for Redundant Arrays of Inexpensive Disks (RAID)” (ACM SIGMOD, June1988, pp. 109-116)

Reference Patent 1: Japanese Patent Laid-open No. (Hei) 9-274544

Reference Patent 2: Japanese Patent Laid-open No. 2002-82775

(Non-Patent Reference 2) “SMI-S Specification Public Review Draft” p.157 (SNIA, 2003)

Problems to be Solved by the Invention

A storage system which moves data in accordance with variouscircumstances in the above-described manner provides a method forachieving optimal location of the data.

However, in the technology disclosed in Patent Reference 1, as describedpreviously, the logical storage regions are monitored, and relocation ofdata starts at the time that the load has exceeded a threshold value.Since relocation of the data takes time to carry out, in cases wherethere is a sudden increase in disk access, the data relocation is notcompleted in time, and, hence, the benefits of relocation cannot beobtained. Moreover, is since the data relocation process generates alarge number of disk access operations, then while relocation is beingexecuted, the disk access operations required for data relocation areadded to the normal disk access operations, and, hence, the overallefficiency declines.

In the technology disclosed in Patent Reference 2, the future dataaccess characteristics are predicted on the basis of past disk accesscharacteristics, and, therefore, relocation is carried out in advance,in accordance with the predictions made. However, it is only possible torespond by means of predictions based on past history in cases where thesame change characteristics are generated in a continuous fashion, atuniform time intervals. Even if the change characteristics are the same,for example, in many cases, disk access occurs in an irregular mannerover time, and, therefore, it is not necessarily possible to predict themost suitable time for relocation of data, on the basis of past diskaccess characteristics. Therefore, in the technology disclosed in PatentReference 2, data is not necessarily relocated in an optimal fashion, asdesired.

On the other hand, there is also the method whereby “hints” definedaccording to SMI-S are provided when creating a new logical volume.However, the SMI-S indicates how existing logical storage regions are tobe used in the future, and it does not consider processing fordetermining the time at which a logical storage region is to berelocated, or the destination to which it is to be relocated.

SUMMARY OF THE INVENTION

The present invention was devised with the foregoing situation in view,an object thereof being to provide technology, for a storage sub-systemcomprising a plurality of storage devices having differentcharacteristics, whereby data is located in the storage device offeringthe most suitable physical storage region, in accordance with the changeof characteristics over time, and the like, required of the physicalstorage region where the data is to be stored.

In order to achieve the aforementioned object, the present invention isprovided with a storage device management device for managing a storagedevice having a plurality of physical storage regions for storing dataused by a computer device.

The storage device managing device comprises: physical storage regioncharacteristics managing means for managing the level of storagecharacteristics provided by each of the plurality of physical storageregions; data storage destination managing means for managing theplurality of physical storage regions and the data stored in eachphysical storage region, by creating associations between the same;characteristics change managing means for managing the previouslydetermined temporal change in the level of the storage characteristicsrequired of the storage destination physical storage region by the datamanaged by the data storage destination managing means; and movementinstructing means for acquiring, at prescribed times, the level ofstorage characteristics in the storage destination required by the dataat that time, for each data item managed by the data storage destinationmanaging means, further acquiring the level of storage characteristicsof the physical storage region in which the data is actually stored,from the physical storage region characteristics managing means,comparing the respective levels, and issuing an instruction to thestorage device for the data to be moved to the physical storage regionproviding the required storage characteristics.

(Merits of the Invention)

In an information processing system comprising a computer device, and aplurality of storage devices having different characteristics, in whichdata used by the computer device is stored, it is possible to locatedata in a storage device providing an optimal physical storage region,at an optimal timing, in accordance with a temporal change in thecharacteristics required of the physical storage region, and the like.

Further characteristics of the present invention will become apparentfrom the following description and the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating an overview of the processing accordingto a first embodiment of the invention;

FIG. 2 is a diagram illustrating the movement of logical volumesaccording to the first embodiment of the invention;

FIG. 3 is a block diagram of an information processing system accordingto the first embodiment of the invention;

FIG. 4 is a block diagram of a high-end storage device and mid-rangestorage device according to the first embodiment of the invention;

FIGS. 5A to 5D show tables located in the memories of respective storagedevice control sections of a high-end storage device and a mid-rangestorage device according to the first embodiment of the invention,wherein FIG. 5A is a diagram of the composition of a logical/physicalmapping table, FIG. 5B is a diagram of the composition of an externalstorage region flag table, FIG. 5C is a diagram of the composition of anexternal logical volume table, and FIG. 5D is a diagram of thecomposition of a logical/physical mapping table of a mid-range storagedevice;

FIG. 6 is a block diagram of an application server according to thefirst embodiment of the invention;

FIG. 7 is a block diagram of a management server according to the firstembodiment of the invention;

FIG. 8 is a diagram showing the composition of a data back-up tableaccording to the first embodiment of the invention;

FIG. 9 is a diagram showing the composition of a replication tableaccording to the first embodiment of the invention;

FIG. 10 is a diagram showing the composition of a cache control tableaccording to the first embodiment of the invention;

FIG. 11 is a diagram showing the composition of a physical storageregion characteristics table according to the first embodiment of theinvention;

FIG. 12A is a diagram showing the composition of a performance changecharacteristics table according to a first embodiment of the invention,and FIG. 12B is a diagram showing the composition of the volume movementinformation table (performance) according to a first embodiment of theinvention;

FIG. 13 is a diagram showing the composition of a performance changegraph table according to the first embodiment of the invention;

FIG. 14(A) is a diagram showing the composition of an availabilitychange characteristics table according to the first embodiment of theinvention, and FIG. 14(B) is a diagram showing the composition of avolume movement information table (availability) according to the firstembodiment of the invention;

FIG. 15 is a diagram showing the composition of an availability changegraph table according to the first embodiment of the invention;

FIG. 16 is a diagram showing the composition of data attribute/changecharacteristics table according to the first embodiment of theinvention;

FIG. 17 is a diagram illustrating one example of a logical volumeallocation screen according to the first embodiment of the invention;

FIG. 18 is a diagram showing the composition of logical volume/dataattribute table according to the first embodiment of the invention;

FIG. 19 is a diagram illustrating the movement of logical volumesaccording to the first embodiment of the invention;

FIG. 20 is a block diagram of an information processing system accordingto a second embodiment of the invention;

FIG. 21 is a diagram illustrating an overview of the processingaccording to the second embodiment of the invention;

FIG. 22 is a diagram illustrating the movement of files according to thesecond embodiment of the invention;

FIG. 23 is a diagram showing the composition of a file system tableaccording to the second embodiment of the invention; and

FIG. 24 is a diagram showing the composition of a movement scheduletable according to the first embodiment of the invention.

DESCRIPTION OF THE PREFERRED EMBODIMENTS First Embodiment

Below, a first embodiment of the present invention will be described.

Before describing the detailed composition, and the like, of the presentembodiment, an overview of the processing according to the presentembodiment will be described with reference to FIG. 1 and FIG. 2. In thepresent embodiment, the access destination recognized by the hostcomputer (application server) is called a “logical volume”.

FIG. 1 is a diagram which will be referred to for the purpose ofdescribing a particular logical volume, the data attribute of datalocated in that logical volume, and the temporal change in thecharacteristics required of a physical storage region forming a storagedestination for data having those data attributes.

The data attribute 7010 is a name assigned to a state of temporal changein the characteristics required of a physical storage region by the datastored in the logical volume in question. Various representative datanames are assigned, indicating the particular circumstances of thechange. For example, names, such as monitoring data, mail log data, orthe like, are assigned. In the present embodiment, the performanceindicating the access speed and the availability indicating the speed ofrecovery, are considered as characteristics required of the physicalstorage region by the data.

The performance change characteristics graph 7020 is a graph is showingthe temporal change of the performance required of the physical storageregion, by data that corresponds to the data attribute 7010. Thevertical axis shows the required performance and the horizontal axisshows time.

The availability change characteristics graph 7030 is a graph showingthe temporal change of the availability required of the physical storageregion, by data that corresponds to the data attribute 7010. Thevertical axis shows the required performance and the horizontal axisshows time.

The logical volume ID 7040 is an identifier for the logical volume inwhich data having the data attribute 7010 is stored.

FIG. 2 is a diagram which illustrates a situation where the logicalvolume, in which the data having the data attribute shown in FIG. 1 isstored, moves between physical storage regions of the storage device inaccordance with previously determined temporal change in the performanceand availability required of the physical storage region by the data inquestion.

Initially the logical volume 7000 identified by the logical volume ID7040 is assigned to a physical storage region 1163 having both a lowperformance and a low availability. Thereupon, in order to respond tothe increase in the required availability, over the passage of time, asindicated by the availability change characteristics graph 7030, thelogical volume 7000 moves to the physical storage region 1162, which hasa low performance and a medium availability (movement step 7051).

Thereupon, in order to respond to a further increase in the requiredavailability, in accordance with the availability change characteristicsgraph 7030, the logical volume 7000 moves to the physical storage region1161 which has a low performance and a high availability (movement step7052).

Thereupon, in order to respond to a sudden increase in the requiredperformance, in accordance with the performance change characteristicsgraph 7020, the logical volume 7000 moves to a physical storage region1061 which has both a high performance and a high availability (movementstep 7053).

Thereupon, in order to respond to a sudden decrease in the requiredperformance, in accordance with the performance change characteristicsgraph 7020, and a sudden decrease in the required availability inaccordance with the availability change characteristics graph 7030, thelogical volume 7000 moves to the physical storage region 1163 which hasboth a low performance and a low availability (movement step 7054).

The composition and processing procedure required in order to achievemovement of the logical volume of this kind will be described in detail.

(System Composition)

FIG. 3 is a block diagram of an information processing system accordingto the present embodiment.

As shown in this diagram, the information processing system according tothe present embodiment comprises a high-end storage device 1000, amid-range storage device 1100, a disk array type back-up device 2000, atape library 2100, a switch 3000, an application server 4000, and amanagement server 5000.

The high-end storage device 1000 is a storage device which stores dataused by the application server 4000. The high-end storage device 1000 isconnected to the switch 3000 via a storage I/F 1010. Moreover, thehigh-end storage device 1000 is also connected to the mid-range storagedevice 1100 by means of an external connection I/F 1030 and a storageI/F 1110.

The mid-range storage device 1100 is a storage device which stores dataused by the application server 4000. The mid-range storage device 1100is connected to the high-end storage device 1000 via a storage I/F 1110and the external connection I/F 1030. The application server 4000performs access via the high-end storage device 1000, whenever it is touse data stored in the mid-range storage device 1100.

The high-end storage device 1000 is able to handle the storage region ofthe mid-range storage device 1100 in the same manner as a storage regioncontained in the high-end storage device 1000. Therefore, theapplication server 4000 is able to handle a storage region of themid-range storage device 1100 in the same manner as a storage region ofthe high-end storage device 1000. In the present embodiment, thehigh-end storage device 1000 has a higher performance, as will bedescribed hereinafter, than the mid-end storage device 1000.

The disk array type back-up device 2000 constitutes a device for backingup the data stored in the high-end storage device 1000 and the mid-rangestorage device 1100. The disk array type back-up device 2000 isconnected to the high-end storage device 1000 by means of a storage I/F2010, the switch 3000, and the storage I/F 1010.

The tape library 2100 constitutes a device for backing up the datastored in the high-end storage device 1000 and the mid-range storagedevice 1100. The tape library 2100 is connected to the high-end storagedevice 1000 by means of a storage I/F 2110, the switch 3000, and thestorage I/F 1010.

The application server 4000 is a computer device which executes anapplication program using data located in the high-end storage device1000 and the mid-range storage device 1100. The application server 4000is connected to the high-end storage device 1000 by means of a storageI/F 4010, the switch 3000, and the storage I/F 1010.

The management server 5000 is a computer device for managing thehigh-end storage device 1000, the mid-range storage device 1100 and theapplication server 4000. The management server 5000 is connected to thehigh-end storage device 1000 by means of a management I/F 5020 and amanagement I/F 1020. Moreover, the management server 5000 is connectedto the mid-range storage device 1100 by means of the management I/F 5020and a management I/F 1120. Moreover, the management server 5000 isconnected to the application server 4000 by means of the management I/F5020 and a management I/F 4020. Furthermore, the management server 5000is connected to the high-end storage device 1000 by means of the switch3000 and the storage I/F 1010.

Next, the high-end storage device 1000 and the mid-range storage device1100 shall be described.

FIG. 4 is a diagram of the composition of the high-end storage device1000 and mid-range storage device 1100.

The high-end storage device 1000 comprises a storage device controlsection 1040 for controlling various processes in the storage device,and a disk section 1080 for storing data.

The storage device control section 1040 comprises a CPU 1041, a cache1043, a memory 1045, a disk adapter 1050, a storage I/F 1010, amanagement I/F 1020, and an external connection I/F 1030. The respectivemodules constituting the storage device control section 1040 areconnected to each other in a mutually connectable fashion.

Furthermore, an I/O control program 1042, a volume movement program1044, a logical/physical mapping table 1046, an external storage regionflag table 1047 and an external logical volume table 1048 are providedin the memory 1045.

The CPU 1041 performs various functions of the high-end storage device1000, by executing respective programs, using the data stored in therespective tables.

Moreover, the storage device control section 1040 is connected to aparity group 1060 and a parity group 1070 of a disk section 1080 bymeans of the disk adapter 1050. The parity group 1060 comprises aphysical storage region 1061, a physical storage region 1062 and aphysical storage region 1063. The parity group 1070 comprises a physicalstorage region 1071, a physical storage region 1072 and a physicalstorage region 1073.

The mid-range storage device 1100 comprises a storage device controlsection 1140 for controlling various processes in the storage device,and a disk section 1170 for storing data.

The storage device control section 1140 comprises a CPU 1141, a cache1143, a memory 1145, a disk adapter 1150, a storage I/F 1110, and amanagement I/F 1120. The respective modules constituting the storagedevice control section 1140 are connected to each other in a mutuallyconnectable fashion.

Furthermore, an I/O control program 1142, a logical/physical mappingtable 1146, and a volume movement program 1144 are stored in the memory1145.

The CPU 1141 performs various functions of the mid-range storage device,by executing respective programs, using the data stored in the memory1145.

Moreover, the storage device control section 1140 is connected to aparity group 1160 of a disk section 1170 by means of the disk adapter1150. The parity group 1160 contains a physical storage region 1161, aphysical storage region 1162 and a physical storage region 1163.

Next, the various tables held in the memory 1045, and the table held inthe memory 1145 will be described.

The logical/physical mapping table 1046 holds information whichassociates logical volumes of the high-end storage device 1000 used bythe application server 4000 as a storage region with physical storageregions in the high-end storage device 1000.

FIG. 5A is a diagram of the composition of a logical/physical mappingtable 1046. In the logical/physical mapping table 1046, the logicalvolume ID 10461 is the identifier for a logical volume provided by thehigh-end storage device 1000 to the application server 4000. The paritygroup ID 10462 is the identifier for the parity group in which thelogical volume identified by the logical volume ID 10461 is located. Thephysical storage region ID 10463 is the identifier of the physicalstorage region in which the logical volume identified by the logicalvolume ID 10461 is located. The address in physical storage region 10464is information representing the position within the physical storageregion at which the logical volume identified by the logical volume ID10461 is located.

The external storage region flag table 1047 holds information indicatingthe respective location of the physical storage region of each logicalvolume provided by the high-end storage device 1000 to the applicationserver 4000. In the present embodiment, this table stores informationindicating whether the storage region is located within the high-endstorage device 1000, or whether it is located in another storage deviceconnected via the external connection I/F 1030.

FIG. 5B is a diagram of the composition of the external storage regionflag table 1047. As the diagram shows, the logical volume ID 10471 is anidentifier for a storage region provided by the high-end storage device1000 to the application server 4000. The external storage region flag10472 is information representing whether or not the logical volumeidentified by the logical volume ID 10471 is located in a physicalstorage region contained within the high-end storage device 1000. In thepresent embodiment, if the value of the external storage region flag10472 corresponding to a logical volume ID 10471 is zero, then thisindicates that the logical volume identified by the logical volume ID10471 is located in a physical storage region within the high-endstorage device 1000. Moreover, if the value of the external storageregion flag 10472 corresponding to a logical volume ID 10471 is 1, thenthis indicates that the logical volume identified by the logical volumeID 10471 is located in a physical storage region within a separatestorage device connected via the external connection I/F 1030.

The external logical volume table 1048 holds information indicating thestorage location of those logical volumes of the logical volumesprovided by the high-end storage device 1000 to the application server4000, that are located in a physical storage region contained in aseparate storage device connected via the external connection I/F 1030.In the present embodiment, this table stores information whichassociates a logical volume in the high-end storage device 1000 with alogical volume in the other storage device where the physical storageregion is located.

FIG. 5C is a diagram showing the composition of an external logicalvolume table 1048. The logical volume ID 10481 is an identifier for astorage region provided by the high-end storage device 1000 to theapplication server 4000. The storage device ID 10482 is an identifierindicating a storage device connected to via the external connection I/F1030, in which the physical storage region of the logical volumeidentified by the logical volume ID 10481 is located. The externallogical volume ID 10483 is an identifier for a logical volume in anexternally connected storage device, which corresponds to the logicalvolume identified by the logical volume ID 10481.

The logical/physical mapping table 1146 holds information whichassociates logical volumes of the mid-range storage device 1100 providedto the high-end storage device 1000 as an externally connected storageregion, with physical storage regions inside the mid-range storagedevice 1100.

FIG. 5D is a diagram of the composition of the logical/physical mappingtable 1146. The logical volume ID 11461 is an identifier for a logicalvolume provided by the mid-range storage device 1100 to the high-endstorage device 1000. The parity group ID 11462 is the identifier for theparity group in which the logical volume identified by the logicalvolume ID 11461 is located. The physical storage region ID 11463 is theidentifier of the physical storage region in which the logical volumeidentified by the logical volume ID 11461 is located. The address inphysical storage region 11464 is information representing the positionwithin the physical storage region at which the logical volumeidentified by the logical volume ID 11461 is located.

The volume movement program 1044 changes the physical storage region towhich a logical volume is assigned in accordance with instructions fromthe management server 5000. In other words, it copies the data at theaddress assigned to the logical volume, from the physical storage regionto which it is initially assigned, to an address in a differentallocation destination storage region, and it rewrites the relatedinformation in the respective tables 1046, 1047 and 1048.

The volume movement program 1144 rewrites the logical/physical mappingtable in accordance with instructions from the high-end storage device1000.

The I/O control programs 1041, 1142 process acquisition requests fordata contained in the high-end storage device 1000 or mid-range storagedevice 1100, input via the storage I/Fs 1010, 1110, and they obtain thedata from the hard disk drive on which it is stored and transmit thedata via the storage I/Fs 1010, 1110.

Next, the application server 4000 shall be described. FIG. 6 is adiagram of the composition of the application server 4000. Theapplication server 4000 comprises a storage I/F 4010, a management I/F4020, a CPU 4030, a memory 4040, a display device 4070 and input means4080. The respective modules constituting the application server 4000are connected to each other in a mutually communicable fashion.

The memory 4040 stores an application program 40401 and a storage devicemanagement client program 40402, and the CPU 4030 performs the variousfunctions of the application server 4000 by loading the respectiveprograms from the memory 4040.

The storage device management client program 40402 transmits logicalvolume allocation requests and logical volume access requests, and thelike, received from a client via the input means 4080, to the managementserver.

(Accessing Storage)

Here, a mode is described wherein the application server 4000 performsaccess to the high-end storage device 1000 and to the mid-range storagedevice 1100 via the high-end storage device 1000.

(Accessing the High-End Storage Device)

During execution of the application program 40401, if there is a commandto access a storage region of logical volume ID “Volume 1” in thehigh-end storage device 1000, then the CPU 4030 performs access to thelogical volume ID “Volume 1”, via the storage I/F 4010, in accordancewith the storage device management client program 40402.

The access command to the logical volume ID “Volume 1” of the high-endstorage device 1000 is transmitted via the switch 3000 and the storageI/F 1010 to the storage device control section 1040 in the high-endstorage device 1000.

Upon receiving the access command for “Volume 1” from the applicationserver 4000, the CPU 1041 carries out processing in accordance with theI/O control program 1042.

Firstly, the CPU 1041 refers to the external storage region flag table1047 and identifies the location of the logical volume designated as theaccess destination. In the case of the example shown in FIG. 5B, the CPU1041 recognizes that the external storage region flag 10472,corresponding to the entry “Volume 1” in the logical volume ID 10471, is“0”, and therefore it judges that the logical volume identified by thelogical volume ID “Volume 1” is located in a physical storage regioncontained within the high-end storage device 1000.

Thereupon, the CPU 1041 refers to the logical/physical mapping table1046 and acquires the parity group ID, physical storage region ID andthe physical storage region address for the designated logical volume.In the example shown in FIG. 5A, the CPU 1041 acquires respective valuesof “1060” for the parity group ID 10462, “1061” for the physical storageregion ID 10463, and “0-1023” for the address in physical storage region10464, corresponding to an logical volume ID 10461 of “Volume 1”.

The CPU 1041 then accesses the address range 0-1023 in the physicalstorage region 1061 of the parity group 1060 via the disk adapter 1050.

Finally, the CPU 1041 sends the value of the access result to theapplication server 4000 via the storage I/F 1010. The value of theaccess result thus transmitted reaches the application server 4000 viathe switch 3000 and the storage I/F 4010.

When the access result value reaches the application server 4000, theCPU 4030 executes the next step in the application program 40401.

(Access to Externally Connected Storage (Mid-range Storage Device 1100))

During execution of the application program 40401, if there is a commandto access a storage region of logical volume ID “Volume 3” in thehigh-end storage device 1000, then the CPU 4030 performs access to thelogical volume ID “Volume 3”, via the storage I/F 4010.

The access command to the logical volume ID “Volume 3” of the high-endstorage device 1000 is transmitted via the switch 3000 and the storageI/F 1010 to the storage device control section 1040 in the high-endstorage device 1000.

Upon receiving the access command for “Volume 3” from the applicationserver 4000, the CPU 1041 carries out processing in accordance with theI/O control program 1042.

Firstly, the CPU 1041 refers to the external storage region flag table1047 and identifies the location of the logical volume designated as theaccess destination. In the case of the example shown in FIG. 5B, the CPU1041 recognizes that the external storage region flag 10472corresponding to the entry “Volume 3” in the logical volume ID 10471, is“1”, and therefore it judges that the logical volume identified by thelogical volume ID “Volume 3” is located in a physical storage regioncontained in a separate storage device connected via the externalconnection I/F 1030.

Thereupon, the CPU 1041 refers to the external logical volume table 1048and acquires information relating to the storage device to which thelogical volume in question belongs, and information relating to thelogical volume in that storage device. In other words, in the exampleillustrated in FIG. 5C, the CPU 1041 acquires information values of“1100” for the storage device ID, and “Volume 1” for the externallogical volume ID, corresponding to the external logical volume ID10481, “Volume 3”.

The CPU 1041 then performs access to the logical volume ID “Volume 1” inthe mid-range storage device 1100, which has a storage device ID of“1100”, by means of the external connection I/F 1030.

The access command to the logical volume ID “Volume 1” of the mid-rangestorage device 1100 is transmitted via the storage I/F 1110 to thestorage device control section 1140 of the mid-range storage device1100.

Upon receiving the access command for “Volume 3” from the high-endstorage device 1000, the CPU 1141 carries out processing in accordancewith the storage device control program 1149.

The CPU 1141 refers to the logical/physical mapping table 1146, and itacquires the parity group ID, the physical storage region ID, and thephysical storage region address for the designated logical volume. Inthe example shown in FIG. 5D, the CPU 1141 acquires respective values of“1160” for the parity group ID 11462, “1161” for the physical storageregion ID 11463, and “0-1023” for the address in physical storage region11464, corresponding to a logical volume ID 11461 of “Volume 1”. The CPU1141 then accesses the address range 0-1023 in the physical storageregion 1161 of the parity group 1160 via the disk adapter 1150.

Finally, the CPU 1141 sends the value of the access result to thehigh-end storage device 1000 via the storage I/F 1110. The access resultvalue thus transmitted reaches the storage device control section 1040in the high-end storage device 1000 via the external connection I/F1030.

When the access result value reaches the storage control section 1040,the CPU 1041 transmits the access result value to the application server4000 by means of the storage I/F 1010. The value of the access resultthus transmitted reaches the application server 4000 via the switch 3000and the storage I/F 4010.

When the access result value reaches the application server 4000, theCPU 4030 executes the next step in the application program 40401.

A process for accessing the high-end storage device 1000, and the like,from the application server has been described.

Next, the management server 5000 shall be described. FIG. 7 is a diagramof the composition of the management server 5000.

The management server 5000 comprises a storage I/F 5010, a managementI/F 5020, a CPU 5030 and a memory 5040. The respective modulesconstituting the management server 5000 are connected to each other in amutually communicable fashion.

The memory 5040 stores a storage device management server program 5041,a cache control program 5042, a cache control table 5043, a replicationcontrol program 5044, a replication table 5045, a data back-up program5046, a data back-up table 5047, a physical storage region table 5048, aperformance change characteristics table 5049, an availability changecharacteristics table 5050, a volume movement information table(performance) 5051, a performance change graph table 5052, anavailability change graph table 5053, a data attribute/changecharacteristics table 5054, a logical volume/data attribute table 5055,and a volume movement information table (availability) 5056.

In the management server 5000, the CPU 5030 performs the respectivefunctions of the management server 5000 by loading the respectiveprogram stored in the memory 5040 and executing the same using data fromthe respective tables.

In the present embodiment, indicators representing performance andavailability are established for each of the respective physical storageregions provided in the high-end storage device 1000 and the mid-rangestorage device 1100. The settings of these indicators do not relatesolely to location, namely whether the relevant physical storage regionis located in the high-end storage device 1000 or the mid-range storagedevice 1100, but rather, they are determined according to whether or notprocessing for increasing the performance or availability, such asback-up, replication, caching, or the like, has been carried out for therespective physical storage regions.

Here, back-up processing means processing for copying the data stored inthe high-end storage device 1000 or the mid-range storage device 1100,to a further device other than the storage devices in question, atprescribed time intervals, and replication processing means processingfor reproducing the data stored in the high-end storage device 1000 orthe mid-range storage device 1100 to a location within the same storagedevice.

A method will be described for setting characteristics based on theperformance and availability of each physical storage region by usingthe programs and tables provided in the management server 5000. Inaccordance with the present embodiment, an example will be describedwherein there are three types of indicator settings for the performanceand availability, namely, “high”, “medium”, and “low”, but the indicatorsettings are not limited to these.

(Back-Up Management)

Firstly, back-up processing carried out in the management server 5000 onthe basis of the data back-up program 5046 and the data back-up table5047 will be described. The back-up processing described in connectionwith the present embodiment involves backing up the data stored in thehigh-end storage device 1000 or the mid-range storage device 1100 toanother device in the same storage system, for example, the disk arraytype back-up device 2000, or the tape library 2100, at prescribed timeintervals. By means of this processing, it is possible to increase thesafety of the data stored in the respective storage device, and, hence,recovery processing can be performed readily in the case of anirregularity, such as damaging of the data holding region in the storagedevice, or the like.

Firstly, the data back-up table 5046 which stores data used in back-upprocessing will be described. The back-up table 5046 is previously inputand saved by an administrator, or the like.

FIG. 8 is a diagram showing the composition of the data back-up table5047. The storage device ID 50471 is an identifier for the storagedevice in which the physical storage region to be backed up is located.The physical storage region ID 50472 is an identifier for the physicalstorage region to be backed up, in the high-end storage device 1000 orthe mid-range storage device 1100. The back-up device ID 54073 is anidentifier for the back-up device which backs up the data from thephysical storage region to be backed up, as identified by the storagedevice ID 50471 and the physical storage region ID 50472. The back-updevice characteristics 50474 is information indicating the performanceof the back-up device identified by the back-up device ID 50473.

The back-up device characteristics 50474, which indicates theperformance of the back-up destination for the data stored in therespective physical storage regions, is an indicator for determining theavailability of the respective physical storage regions.

The data back-up program 5046 is called and executed periodically by thestorage device management server program 5041 implemented by the CPU5030.

When the storage device management server program 5041 calls the databack-up program 5046, firstly, the CPU 5030 acquires information on thestorage device ID 50471 and the physical storage region ID 50472, andthe back-up device ID 50473, from the data back-up table 5047.

The CPU 5030 executes the data back-up program 5046 and sends a commandfor the data in the physical storage region identified by the storagedevice ID 50471 and the physical storage region ID 50472 to be backed upto the back-up device identified by the back-up device ID 50473,(hereinafter, called a back-up command), to the storage device controlsection 1040 of the high-end storage device 1000, via the storage I/F5010, the switch 3000 and the storage I/F 1010.

When the back-up command reaches the storage device control section1040, in accordance with the I/O command program 1042, the CPU 1041acquires the data in the physical storage region designated in theback-up command via the disk adapter 1050 or the external connection I/F1030, and backs up this data to the designated back-up device, via thestorage I/F 1010 and the switch 3000.

For example, in the case of the example shown in FIG. 8, the data in thephysical storage region 1061, the physical storage region 1062, thephysical storage region 1071 and the physical storage region 1072 in thehigh-end storage device 1000, and the data in the physical storageregion 1161 and the physical storage region 1162 in the mid-rangestorage device 1100, is backed up to the disk array type back-up device2000. Furthermore, in this scenario, the data in the physical storageregion 1063, and the physical storage region 1073 of the high-endstorage device 1000, and the data in the physical storage region 1163 ofthe mid-range storage device 1100, is backed up to the tape library2100.

(Replication Management)

Next, the replication processing carried out by the management server5000 on the basis of the replication control program 5044 and thereplication table 5045 will be described. The replication processing inthe present embodiment is processing for generating a replicate copy ofthe designated physical storage region within the same storage device.In the present embodiment, a replicate is generated for physical storageregions designated in the replication table 5045.

The fact that replication processing is or is not carried out for aparticular physical storage region is used as an indicator whendetermining the availability of that physical storage region, as will bedescribed hereinafter. For example, a physical storage device for whichreplication processing is carried out will be judged to have a “high”availability.

Firstly, the replication table 5045 which stores data used inreplication processing will be described. The back-up table 5045 ispreviously input and saved by an administrator, or the like.

FIG. 9 is a diagram showing the composition of the replication table5045. The storage device ID 50451 is an identifier for the storagedevice in which the physical storage region to be replicated is located.The physical storage region ID 50452 is an identifier for the physicalstorage region in the storage device, of which a replicate copy is to becreated.

The replication control program 5044 is called and executed by thestorage device management server program 5041 implemented by the CPU5030 at start-up.

Firstly, the CPU 5030 acquires information relating to the storagedevice ID 50451 and the physical storage region ID 50452 from thereplication table 5045.

The CPU 5030 then executes the replication control program 5044, and itsends a command for a replicate copy of the physical storage regionidentified by the storage device ID 50451 and the physical storageregion ID 50452 to be created within the same storage device, via thestorage I/F 5010, the switch 3000, and the storage I/F 1010, to thestorage device control section 1040 of the high-end storage device 1000.

When the replicate creation command reaches the storage device controlsection 1040, in accordance with the I/O control program 1042, the CPU1041 of the high-end storage device 1000 determines whether or not thephysical storage region designated by the physical storage region ID50452, of which a replicate copy is to be created, is located within thehigh-end storage device 1000. If the physical storage region in questionis located within the high-end storage device 1000, then the CPU 1041accesses the designated physical storage region by means of the diskadapter 1050, and creates a replicate copy of that physical storageregion.

If the physical storage region in question is located in the mid-rangestorage device 1100, then the CPU 1041 sends a replicate creationcommand to the storage device control section 1140 of the mid-rangestorage device 1100 via the external connection I/F 1030 and the storageI/F 1110. When the replication creation command reaches the storagedevice control section 1140, in accordance with the I/O control program1142, the CPU 1141 of the mid-range storage device 1100 accesses thedesignated physical storage region, via the disk adapter 1150, andcreates a replicate of that physical storage region.

In the case of the example shown in FIG. 9, the physical storage region1061 and the physical storage region 1071 in the high-end storage device1000, and the physical storage region 1161 in the mid-range storagedevice 1100, respectively, have replicate copies within the same storagedevice.

<Cache Management>

Next, the cache processing, which is carried out by the managementserver 5000 on the basis of the cache control program 5042 and the cachecontrol table 5043, will be described. The cache processing in thepresent embodiment is used for placing data stored in the designatedphysical storage region on the cache as resident data. In the presentembodiment, the data in the physical storage regions designated by thecache control table 5043 is placed on the cache as resident data.

The fact that cache processing is or is not carried out for a particularphysical storage region is used as an indicator for determining theperformance of the physical storage region in question, as will bedescribed hereinafter. In other words, if cache processing is carriedout, then it is possible to improve the access performance to thephysical storage region in question, and, hence, that physical storageregion is judged to have a “high” performance.

Firstly, the cache control 5043 which stores data used in cacheprocessing will be described. The cache control table 5043 is previouslyinput and saved by an administrator, or the like.

FIG. 10 is a diagram showing the composition of the cache control table5043. The storage device ID 50431 is an identifier for the storagedevice in which the physical storage region, whose data is to be placedas resident data on the cache, is located. The physical storage regionID 50432 is an identifier for the physical storage region in the storagedevice, whose data is to be placed as resident data on the cache.

The cache control program 5042 is called and executed by the storagedevice management server program 5041 implemented by the CPU 5030 at isstart-up.

Firstly, the CPU 5030 acquires information about the storage device ID50431 and the physical storage region ID 50432 from the cache controltable 5043.

The CPU 5030 then executes the cache control program 5042 and sends acommand for the physical storage region identified by the storage deviceID 50431 and the physical storage region ID 50432 to be placed asresident data on the cache via the storage I/F 5010, the switch 3000,and the storage I/F 1010, to the storage device control section 1040 ofthe high-end storage device 1000.

When the caching command reaches the storage device control section1040, in accordance with the I/O control program 1042, the CPU 1041 ofthe high-end storage device 1000 determines whether or not the physicalstorage region designated by the physical storage region ID 50432, whichis the object of the caching command, is located within the high-endstorage device 1000. If the physical storage region in question islocated within the high-end storage device 1000, then the CPU 1041 readsout the data of the physical storage region via the disk adapter 1050and writes the data to the cache 1043.

If the physical storage region in question is located in the mid-rangestorage device 1100, then the CPU 1041 sends a caching command to thestorage device control section 1140 of the mid-range storage device 1100via the external connection I/F 1030 and the storage I/F 1110. When thecaching command reaches the storage device control section 1140, inaccordance with the I/O control program 1142, the CPU 1141 of themid-range storage device 1100 accesses the designated physical storageregion via the disk adapter 1150, reads out the data from that physicalstorage region, and writes the data to the cache 1143.

In the case of the example shown in FIG. 10, the physical storage region1061, the physical storage region 1062 and the physical storage region1063 in the high-end storage device are resident on the cache.

(Setting the Physical Storage Region Characteristics)

As described above, performance and availability characteristics are setfor each of the physical storage regions provided in the high-endstorage device 1000 and the mid-range storage device 1100, according towhether or not the aforementioned back-up processing, replicationprocessing or caching processing are carried out with respect to thatphysical storage region. The characteristics of each physical storageregion are stored and held in the physical storage regioncharacteristics table 5048 by the storage device management serverprogram 5041. Below, a procedure for storing the characteristics of eachphysical storage region in the physical storage region characteristicstable 5048 by means of the storage device management server program 5041will be described.

The CPU 5030 judges the characteristics of each physical storage regionin accordance with the processing carried out with respect to the same,and it creates a physical storage region characteristics table 5048accordingly by executing the aforementioned cache control program 5042,replication control program 5044 and data back-up program 5046 inaccordance with the storage device management server program 5041, andthen referring to the data back-up table 5047, the replication table5045 and the cache control table 5043 generated thereby.

Here, the composition of the physical storage region characteristicstable 5048 will be described. FIG. 11 is a diagram showing thecomposition of the physical storage region characteristics table 5048.As shown in this diagram, the physical storage region characteristicstable 5048 comprises a storage device ID 50481, a physical storageregion ID 50482, performance characteristics 50483, and availabilitycharacteristics 50484.

In accordance with the storage device management server program 5041,the CPU 5030 acquires the storage device IDs 50471, physical storageregion IDs 50472, and back-up device characteristics 50474 from the databack-up table 5047. It then writes the acquired storage device IDs 50471to the storage device IDs 50481 in the physical storage regioncharacteristics table 5048 and writes the physical storage region IDs50472 to the physical storage region IDs 50482, respectively.

Thereupon, the CPU 5030 writes “medium” or “low” as an indicatorrepresenting availability to the availability characteristics 50484column in accordance with the value stored in the back-up devicecharacteristics 50474 column. In other words, if the value stored in theback-up device characteristics 50474 is “high-speed”, then “medium” iswritten to the availability characteristics 50484; and, if the value ofthe back-up device characteristics 50474 is “low-speed”, then “low” iswritten to the availability characteristics 50484.

Next, the CPU 5030 acquires the storage device IDs 50451 and thephysical storage region IDs 50452 from the replication table 5045. TheCPU 5030 then refers to the storage device IDs 50481 and the physicalstorage region IDs 50482 already stored in the physical storage regioncharacteristics table 5048, and it searches for combinations which matchthe storage device IDs 50451 and the physical storage region IDs 50452thus acquired. If a matching combination is found, then the CPU 5030writes “high” to the availability characteristics 50484 corresponding tothat particular combination.

Next, the CPU 5030 refers to the storage device IDs 50481 in thephysical storage region characteristics table 5048 and writes theperformance characteristics 50483 in accordance with the performance ofthe actual storage device. In the present embodiment, if the ID of thehigh-end storage device 1000, namely, “1000”, is written, then “medium”is written as the corresponding value for performance characteristics50483; and, if the ID of the mid-range storage device 1100, namely,“1100”, is written, then “low” is written as the corresponding value forperformance characteristics 50483.

The CPU 5030 then acquires the storage device IDs 50431 and the physicalstorage region IDs 50432 from the cache control table 5043. Next, theCPU 5030 refers to the storage device IDs 50481 and the physical storageregion IDs 50482 in the physical storage region characteristics table5048, and it searches for any combinations which match the combinationsof storage device IDs 50431 and physical storage region IDs 50432. If amatching combination is found, then the CPU 5030 writes “high” to theperformance characteristics 50483 corresponding to that particularcombination.

By means of the foregoing procedure, the CPU 5030 generates a physicalstorage region characteristics table 5048 in accordance with storagedevice management server program 5041.

(Performance Characteristics and Availability Characteristics)

Furthermore, in the present embodiment, information indicatingrespective temporal changes in the performance and the availability, inaccordance with the types of data stored in the storage device, isprepared in advance. This previously prepared information indicatingtemporal change is described below.

In the present embodiment, the management server 5000 comprises aperformance change graph table 5052 and an availability change graphtable 5050 which hold, in graph form, information indicating the generalchange, over time, in the performance and availability required of thestorage region to which a particular logical volume is assigned, inaccordance with the type of data stored in that logical volume, as wellas a volume movement information table (performance) 5051 and a volumemovement information table (availability) 5056, which store informationidentifying the concrete characteristics of a physical storage regionthat is to be moved in accordance with temporal change.

The actual performance characteristics of the movement destination aredetermined and held in the volume movement information table(performance) 5051 and the volume movement information table(availability) 5056, in accordance with the change indicated in theperformance change graph table 5052 and the volume movement informationtable (availability) 5056. In these tables, the particular date and timegiving cause to movement of a logical volume in accordance with atemporal change in the performance or availability (hereinafter, called“volume movement”) is referred to as the established date and time.

FIG. 13 is a diagram showing the composition of the performance changegraph table 5052. As shown in this diagram, the performance change graphtable 5052 comprises performance change graph IDs 50521 and performancechange graphs 50522.

The performance change graph ID 50521 is an identifier for a graphrepresenting a performance change. The performance change graph 50522 isa graph representing the change with the passage of time in theperformance required of the physical storage region, in which the datais stored, for each type of data.

FIG. 15 is a diagram showing the composition of the availability changegraph table 5053. As shown in this diagram, the availability changegraph table 5053 comprises availability change graph IDs 50531 andavailability change graphs 50532.

The availability change graph ID 50531 is an identifier for a graphrepresenting an availability change. The availability change graph 50532is a graph representing the change with the passage of time in theavailability required of the physical storage region, in which the datais stored, for each type of data.

FIG. 12B is a diagram showing the composition of the volume movementinformation table (performance) 5051. As shown in this diagram, thevolume movement information table 5051 comprises volume movementinformation (performance) ID 50511, movement numbers 50512, movementdate and time information 50513, and movement destination performancecharacteristics 50514.

The volume movement information (performance) ID 50511 corresponds tothe respective change characteristics indicated in a performance changegraph 5052, in other words, it corresponds to a performance change graphID 50521.

The movement destination performance characteristics 50514 represent theperformance characteristics of the physical storage region forming thevolume movement destination, in the volume movement at the timingindicated by the movement date and time 50513. This is found bydetermining and storing the level of performance characteristics of thephysical storage regions where the respective data are to be stored, inthe event that the prescribed threshold value is exceeded, on the basisof a change in the performance change graph 50522.

The movement date/time 50513 indicates the timing at which volumemovement is carried out. Similar to the movement destination performancecharacteristics 50514, the date and time at which the aforementionedmovement destination performance characteristics 50514 change on thebasis of the change in the performance change graph 50522 is stored asthe timing at which movement is carried out.

The movement number 50512 is a number that represents a procedure forvolume movement.

FIG. 14(B) is a diagram of the composition of the volume movementinformation table (availability) 5056. As shown in this diagram, thevolume movement information table (availability) 5056 comprises volumemovement information (availability) IDs 50561, movement numbers 50562,movement is date and time information 50563, and movement destinationavailability characteristics 50564.

The volume movement information (availability) ID 50561 corresponds tothe respective change characteristics indicated in an availabilitychange graph 5053; in other words, it corresponds to an availabilitychange graph ID 50531.

The movement destination availability characteristics 50564 representthe availability characteristics of the physical storage region formingthe volume movement destination in the volume movement at the timingindicated by the movement date and time 50563. This is found bydetermining and storing the level of performance characteristics of thephysical storage regions where the respective data are to be stored, inthe event that the prescribed threshold value is exceeded, on the basisof the change in the availability change graph 50522.

The movement date/time 50563 indicates the timing at which volumemovement is carried out. Similarly to the movement destinationavailability characteristics 50564, the date and time at which theaforementioned movement destination availability characteristics 50564change on the basis of the change in the availability change graph 50532is stored as the timing at which movement is carried out.

The movement number 50562 is a number that represents a procedure forvolume movement.

The movement destination availability characteristics 50564 representthe availability characteristics of the physical storage region formingthe volume movement destination in the volume movement at the timingindicated is by the movement date and time 50563.

For example, firstly, a logical volume having data attributes whereinthe volume movement information (availability) ID 50561 is “1” will beassigned to a physical storage region having “high” performancecharacteristics, by means of a procedure indicated by a movement number50562 of “1”. Thereupon, by means of a procedure indicated by a movementnumber 50562 of “2”, it will be reassigned to a physical storage regionhaving “medium” performance characteristics, when one third of the timeperiod from the time of its first assignment until the established dateand time has elapsed. Thereupon, by means of a procedure indicated by amovement number 50562 of “3”, it will be reassigned to a physicalstorage region having “low” performance characteristics, when two thirdsof the time period from the time of its first assignment until theestablished date and time has elapsed.

A logical volume having data attributes wherein the volume movementinformation (availability) ID 50561 is “1”, for example, will beassigned firstly to a physical storage region having “high” availabilitycharacteristics, by means of a procedure indicated by a movement number50562 of “1”. Thereupon, by means of a procedure indicated by a movementnumber 50562 of “2”, it will be assigned to a physical storage regionhaving “medium” availability characteristics, when one third of the timeperiod from the time of its first assignment until the established dateand time has elapsed. Thereupon, by means of a procedure indicated by amovement number 50562 of “3”, it will be assigned to a physical storageregion having “low” availability characteristics, when two thirds of thetime period from the time of its first assignment until the establisheddate and time has elapsed.

In the present embodiment, when the aforementioned established date andtime is determined, then information specifying the established date andtime is held in the performance change characteristics table 5049, theavailability change characteristics table 5050 and the dataattribute/change characteristics table 5054, on the basis of theaforementioned previously stored information indicating the temporalchange in the performance and availability required of the storagedestination corresponding to respective data types. Below, these varioustables will be described.

FIG. 12A is a diagram showing the composition of a performance changecharacteristics table 5049. As shown in the diagram, the performancechange characteristics table 5049 comprises performance changecharacteristics IDs 50491, established date/time names 50492,established date/time information 50493, volume movement information IDs50494, and performance change graph IDs 50495.

The performance change characteristics ID 50491 is an indicator foridentifying the temporal change in the access performance required ofthe storage destination by the data, and it is assigned universally toeach data element stored in the table.

The established date/time name 50492 is the name of the date/time givingrise to a volume movement. For example, if the data is monitoring data,then the name “monitoring date” is assigned; and, if the data is a maillog, then the “storage conditions change date” indicating the day onwhich storage ends is assigned as a name.

The established date/time 50493 is the specific date and time givingrise to a volume movement, as identified by the established date/timename 50492. In the case of monitoring data, this will be the actualmonitoring date, and in the case of a mail log, or the like, it will bethe actual date on which the storage conditions change.

The volume movement information ID 50494 is an identifier foridentifying the volume movement information for each data item stored inthe performance change characteristics table 5049, and it contains avolume movement information (performance) ID 50511 relating to theaforementioned volume movement information (performance) 5051. Forexample, in the case of monitoring data, it contains the value “3” andin the case of a mail log, it contains the value “1”.

The performance change graph ID 50495 is an identifier for identifying agraph showing the temporal change in performance for each data elementstored in the performance change characteristics table 5049, and itcontains a performance change graph ID 50521 relating to thecorresponding performance change graph table 5052.

FIG. 14A is a diagram showing the composition of an availability changecharacteristics table 5050. As shown in the diagram, this tablecomprises availability change characteristics IDs 50501, establisheddate/time names 50502, established date/time information 50503, volumemovement information ID 50504 and availability change graph IDs 50505.

The availability change characteristics ID 50501 is an indicator foridentifying the temporal change in the availability required by thedata, and it is assigned universally to each data element stored in thetable.

The established date/time name 50502 is the name of the date/time givingrise to a volume movement. For example, if the data is monitoring data,then the name “monitoring date” is assigned and, if the data is a maillog, then the name “storage conditions change date” is assigned.

The established date/time 50503 is the specific date and time givingrise to a volume movement, as identified by the established date/timename 50502. In the case of monitoring data, this will be the actualmonitoring date; and, in the case of a mail log, or the like, it will bethe actual date on which the storage conditions change.

The volume movement information ID 50504 is an identifier foridentifying the volume movement information for each data item stored inthe availability change characteristics table 5050, and it containsvolume movement information (availability) IDs 50561 for theaforementioned volume movement information (availability) 5056. Forexample, in the case of monitoring data, it contains the value “3”, andin the case of a mail log, it contains the value “1”.

The availability change graph ID 50505 is an identifier for identifyinga graph showing the temporal change in availability for each dataelement stored in the availability change characteristics table 5050,and it contains an availability change graph ID 50531 relating to thecorresponding availability change graph table 5053.

Here, in the present embodiment, as described above, previously preparedinformation identifying a temporal change in performance andavailability is held in the data attribute/change characteristics table5054 for each data attribute.

FIG. 16 is a diagram showing the composition of the dataattribute/change characteristics table 5054. Volume movement forachieving optimal location of the logical volumes is carried out on thebasis of this table, as will be described hereinafter.

As shown in this diagram, the data attribute/change characteristicstable 5054 comprises data attribute names 50541, performance changecharacteristics IDs 50542 and availability change characteristics IDs50543.

The data attribute name 50541 is the name of a data attribute indicatingthe type of data stored in a logical volume in the storage device. Forexample, in the case of monitoring data with a monitoring date of30^(th) June, the name is “monitoring data with established date & time6/30”; in the case of monitoring data with a monitoring date of 30^(th)September, the name is “monitoring data with established date & time9/30”; and, in the case of a mail log with a storage end date, in otherwords, a storage conditions change date of 15^(th) July, the name is“mail log with established date & time 7/15”, and so on.

The performance change characteristics ID 50542 is informationidentifying the performance change characteristics of data having thedata attribute identified by the data attribute name 50541. Morespecifically, it is the value of a performance change characteristics ID50491 in the performance change characteristics table 5049.

The availability change characteristics ID 50542 is informationidentifying the availability change characteristics of data having thedata attribute identified by the data attribute name 50541. Morespecifically, it is the value of an availability change characteristicsID 50501 in the availability change characteristics table 5050.

(Setting the Data Attribute when Assigning Logical Volumes)

Furthermore, in the present embodiment, a logical volume/data attributetable 5055 is stored which contains information indicating theattributes of the data stored in each one of the logical volumes.

FIG. 18 is a diagram of the composition of the logical volume/dataattribute table 5055. The logical volume/data attribute table 5055comprises logical volume IDs 50551 and data attributes 50552. Thelogical volume ID 50551 is an identifier for identifying a logicalvolume in the high-end storage device 1000. The data attribute 50552 isa data attribute which corresponds to the logical volume identified bythe logical volume ID 50551.

Below, the method used in the management server 5000 for assigninglogical volumes as storage regions to be used by the application server4000 and generating a logical volume/data attribute table 5055 will bedescribed.

In the application server 4000, when an logical volume of the high-endstorage device 1000 is to be assigned as a storage region for use by theapplication program 40401, the application program 40401 calls thestorage device management client program 40402.

The CPU 4030 loads and executes the storage device control clientprogram 40402, and it requests the management server 5000 to assign thelogical volume via the management I/F 4020.

When the management server 5000 receives the logical volume assignmentrequest from the application server 4000, via the management I/F 5020,the CPU 5030 calls the storage device management server program 5041.

The CPU 5030 sends a request to acquire a logical volume list (listacquisition request) to the high-end storage device 1000 via themanagement I/F 5020. In accordance with the I/O control program 1042,the CPU 1041 of the high-end storage device 1000, having received thelist acquisition request via the management I/F 1010, refers to thelogical/physical mapping table 1046, acquires the logical volume IDs10461 therein, and sends same to the management server 5000 via themanagement I/F 1020.

On the other hand, the CPU 5030 of the management server calls thestorage device management server program 5041 and acquires all of thedata attribute names 50541, and the respective performance changecharacteristics IDs 50542 and availability change characteristics IDs50543 that it is holding itself, from the data attribute/changecharacteristics table 5054. The CPU 5030 accesses the performance changecharacteristics table 5049 and the availability change characteristicstable 5050, and it extracts data identified respectively by theperformance change characteristics IDs 50542 and the availability changecharacteristics IDs 50543. Thereupon, the CPU 5030 accesses theperformance change graph table 5052 and the availability change graphtable 5053, and it acquires the performance change graphs 50522 and theavailability change graphs 50532 corresponding to the performance changecharacteristics graph IDs 50495 and the availability change graph IDs50505 of the extracted data.

Furthermore, the CPU 5030 also acquires the logical volume/dataattribute table 5055 in order to obtain information on the IDs oflogical volumes that have been assigned already.

The CPU 5030 sends the logical volume IDs 10461 forming the list oflogical volumes acquired from the high-end storage device 1000, the dataattribute names 50541 acquired in accordance with the storage devicemanagement server program 5041, and the performance change graphs 50522and availability change graphs 50533 corresponding respectively to same,to the application server 4000, by means of the management I/F 5020.

The CPU 4030 of the application server 4000 constructs a logical volumeallocation screen 9000, using the logical volume ID received via themanagement I/F 4020, the data attribute name 50541, performance changegraph 50522, availability change graph 50532, and the logicalvolume/data attribute table 5055, and it displays this screen on adisplay device 4070.

FIG. 17 shows one example of such a display. As shown in the diagram,the logical volume allocation screen 9000 comprises a logical volume IDselection box 9100 for selecting a logical volume storing data, a dataattribute name box 9200 for specifying the attributes of the storeddata, and an OK button for receiving acknowledgement from the user.

The CPU 4030 of the application extracts currently unassigned logicalvolumes, using the logical volume IDs 10461 and the information in thelogical volume/data attribute table 5055, and displays the same in thelogical volume ID selection box 9100. The user is able to select adesired logical volume from the logical volume IDs being displayed.

Furthermore, the CPU 4030 of the application server causes all of thereceived data attribute names 50541 to be displayed in the dataattribute name box 9200 in such a manner that the user can select fromsame. The user is able to select the data attribute that is to be storedin the storage device from the data attribute names displayed in thedata attribute name box 9200.

Furthermore, the CPU 4030 of the application server also causes aperformance change graph 50522 indicating the relevant performancechange characteristics, and an availability change graph 50532indicating the relevant availability change characteristics, to bedisplayed, in coordination with the data attribute displayed as theselection in the data attribute name box 9200. The user is able to referto these graphs when selecting the data attribute.

Furthermore, upon receiving the acknowledgement of the user via the OKbutton 9700, the CPU 4030 of the application server sends the logicalvolume ID 10461 and data attribute 50541 selected by the user in thelogical volume ID selection box 9100 and the data attribute name box9200, respectively, to the management server 5000 via the management I/F4020.

Upon receiving the logical volume ID 10461 and the data attribute 50541via the management I/F 5020, the management server 5000 calls thestorage device management server program 5041 and stores the receivedlogical volume ID 10461 and data attribute 50541 as a new entry in thelogical volume/data attribute table 5055.

In the foregoing, a case was described wherein a performance changecharacteristics table 5049 and availability change characteristics table5050 containing established date and time information are prepared inadvance, but the invention is not limited to this. For instance, thevolume movement information table (performance) 5051, the volumemovement information table (availability) 5056, the performance changegraph table 5052 and the availability change graph table 5054 only areassigned with a data attribute name and held in the management server5000, and they are displayed to the user on the display device 4070 ofthe application server 4000 without established dates and times beingspecified. In addition to accepting selection of a prescribed dataattribute from the data attribute names, as instructed by the user bymeans of the display device 4070, it is also possible to adopt acomposition wherein an instruction of the established date and time andthe specified logical volume is also accepted, and a performance changecharacteristics table 5049, an availability change characteristics table5050 and a logical volume/data attribute table 5055 are generated andsaved by the management server 5000 in accordance with the informationthus received.

(Moving Volumes)

Below, a description will be given of the movement of a logical volumeas performed in the present embodiment over the passage of time, on thebasis of the settings stated above.

Below, the movement of a logical volume having a logical volume ID of“Volume 1” as illustrated in FIG. 18, will be described in detail withreference to FIG. 2, FIG. 5, FIG. 11, FIG. 12A, FIG. 12B, FIG. 14A, FIG.14B and FIG. 16. The logical volume that is moved in not limited to thisone. It is also possible for a plurality of logical volumes to be moved.

In the management server 5000, the CPU 5030 executing the storage devicemanagement server program 5041 monitors the movement date/time 50513 inthe volume movement information table 5051 and the movement date/time50563 in the volume movement information table 5056.

(Movement of Logical Volume “Volume 1”)

At prescribed time intervals, the CPU 5030 refers to the logicalvolume/data attribute table 5055 with respect to the logical volumehaving an logical volume ID 50551 of “Volume 1”, and acquires the dataattribute “monitoring data with established date/time 6/30”, from thedata attribute 50552 for same.

Thereupon, the CPU 5030 refers to the data attribute/changecharacteristics table 5054 with respect to the data attribute“monitoring data with established date/time 6/30”, and acquiresperformance change characteristics ID value of “3” from the performancechange characteristics IDs 50542, and the availability changecharacteristics ID value of “3” from the availability changecharacteristics IDs 50543.

The CPU 5030 then refers to the performance change characteristics table5049 on the basis of the performance change characteristics ID “3”, andacquires a volume movement information ID value of “3” from the volumemovement information IDs 50494. The CPU 5030 then refers to theavailability change characteristics table 5050 on the basis of theavailability change characteristics ID “3”, and acquires a volumemovement information ID value of “3” from the volume movementinformation IDs 50504.

The CPU 5030 refers to the volume movement information table(performance) 5051 and monitors the movement date/time 50513corresponding to volume movement information (performance) ID “3”.

The CPU 5030 also refers to the volume movement information table(availability) 5056 and monitors the movement date/time 50563corresponding to volume movement information (availability) ID “3”.

(Initial Location of Logical Volume “Volume 1”)

Firstly, the CPU 5030 reads in that, immediately after assignment of thelogical volume “Volume 1”, the movement date/time 50513 corresponding tothe combination of a volume movement information (performance) ID 50511of “3” and a movement number 50512 of “1” is “upon creation”, and itacquires the value “low” of the movement destination performancecharacteristics 50514 corresponding to the same.

Simultaneously with this, it reads in that the movement date/time 50563corresponding to the combination of a volume movement information(availability) ID 50561 of “3” and a movement number 50562 of “1” is“upon creation”, and it acquires the value “low” of the movementdestination availability characteristics 50564 corresponding to thesame.

Thereupon, the CPU 5030 refers to the physical storage regioncharacteristics table 5048 in accordance with the storage devicemanagement server program 5041, and it acquires a value of “1100” forthe storage device ID 50481 and a value of “1163” for the physicalstorage region ID 50482 corresponding to the combination of a “low”entry in the performance characteristics 50483 and a “low” entry in theavailability characteristics 50484. Here, if there are plurality ofstorage devices IDs 50481 which correspond to a combination of “low”performance characteristics 50483, and “low” availabilitycharacteristics 50484, then IDs for all of these are acquired. Thisapplies similarly to all of the movement steps described below.

The CPU 5030 sends a request for the logical volume having a logicalvolume ID “Volume 1” to be moved to the physical storage regioncorresponding to the storage device ID “1100” and the physical storageregion ID “1163”, to the high-end storage device 1000, via themanagement I/F 5020 and the management I/F 1020.

When the storage device control section 1040 of the high-end storagedevice 1000 receives the movement request for the logical volume, theCPU 1041 calls the volume movement program 1044.

In accordance with the volume movement program 1044, the CPU 1041 refersto the external storage region flag table 1047 and the logical/physicalmapping table 1046 in the memory 1045, and it acquires informationindicating that the logical volume having an logical volume ID “Volume1” is situated in the physical storage region having a physical storageregion ID “1061”, and that the address within the physical storageregion is “0-1023”.

The CPU 1041 compares the physical storage region ID “1163” to which thelogical volume is to be moved according to the request, with the ID“1061” of the physical storage region to which “Volume 1” is currentlyassigned, and since the two IDs are different, it judges that movementis necessary. At this time, if one of the destination physical storageregion IDs coincides with the ID of the physical storage region to whichthe logical volume is currently assigned, then the logical volume is notmoved. This applies similarly to all of the movement steps describedbelow.

The CPU 1041 recognizes that the storage device ID contained in therequest is “1100”, and it sends a request for the data in the addressrange “0-1023” of the physical storage region 1061 to be copied to thephysical storage region 1163 in the mid-range storage device 1100 viathe external connection I/F 1030 and the storage I/F 1110.

When the storage device control section 1140 of the mid-range storagedevice 1100 receives a data copy request, the CPU 1141 writes thereceived data to the address “1024-2047” of the physical storage region1163, in accordance with the volume movement program 1144.

Thereupon, the CPU 1141 adds information to the logical/physical mappingtable 1146, indicating a logical volume ID 11461 of “Volume 3”, a paritygroup ID 10462 of “1160”, a physical storage region ID of “1163” and anaddress in physical storage region of “1024-2047”.

The volume movement means 1044 sets a value of “1” for the externalstorage region flag 10472 corresponding to a logical volume ID 10471 of“Volume 1” in the external storage region flag table 1047. The volumemovement means 1044 also adds information to the external logical volumetable 1048 indicating an logical volume ID 10481 of “Volume 1”, astorage device ID 10482 of “1100”, and an external logical volume ID10483 of “Volume 3”.

Furthermore, the volume movement means 1044 deletes information relatingto the logical volume ID 10461 “Volume 1” from the logical/physicalmapping table 1046.

(First Movement of Logical Volume “Volume 1”)

Next, the movement step 7051 in the logical volume movement illustratedin FIG. 2 will be described in detail.

With respect to the logical volume having a logical volume ID “Volume1”, when one third of the time period from the time that the logicalvolume was first assigned until the established date/time has elapsed,the CPU 5030 monitoring the movement date/time 50517 corresponding tothe volume movement information (availability) ID “3” reads in the factthat the movement number 50516 is “2” and the movement date/time 50517is “(established date/time−creation date)/3”, and it acquires the value“medium” for the movement destination availability characteristics 50564corresponding to the same.

Thereupon, the CPU 5030 refers to the physical storage regioncharacteristics table 5048, and acquires a value of “1100” for thestorage device ID 50481 and a value of “1162” for the physical storageregion ID 50482 corresponding to the combination of a “low” entry in theperformance characteristics 50483 and a “medium” entry in theavailability characteristics 50484.

The CPU 5030 sends a request for the logical volume having a logicalvolume ID “Volume 1” to be moved to the physical storage regioncorresponding to the storage device ID “1100” and the physical storageregion ID “1162”, to the high-end storage device 1000, via themanagement I/F 5020 and the management I/F 1020.

When the storage device control section 1040 of the high-end storagedevice 1000 receives the movement request for the logical volume, theCPU 1041 processes the request in accordance with the volume movementprogram 1044. The CPU 1041 refers to the external storage region flagtable 1047 and the external logical volume table 1048 in the memory1045, and acquires information indicating that the logical volume havinga logical volume ID of “Volume 1” is the logical volume “Volume 3” ofthe external storage device “1100”.

Thereupon, if it is judged that movement is necessary, the CPU 1041recognizes that the storage device ID contained in the request is“1100”, and sends a request for the data of the logical volume “Volume3” of the mid-range storage device 1100 to be copied to the physicalstorage region 1162 in the mid-range storage device 1100, via theexternal connection I/F 1030 and the storage I/F 1110.

When the storage device control section 1140 of the mid-range storagedevice 1100 receives a data copy request, the CPU 1141 writes the datain the logical volume “Volume 3” to the address “0-1023” of the physicalstorage region 1162, in accordance with the volume movement program1144.

Next, the CPU 1141 changes the physical storage region ID 11463corresponding to the logical volume ID 11461 value of “Volume 3” in thelogical/physical mapping table 1146, to “1162”, and changes the value ofthe address in physical storage region 11464 to “0-1023”.

(Second Movement of Logical Volume “Volume 1”)

Next, the movement step 7052 in the logical volume movement illustratedin FIG. 2 will be described in detail.

With respect to the logical volume having a logical volume ID “Volume1”, when one third of the time period from the time that the logicalvolume was first assigned until the established date/time has elapsed,the CPU 5030 monitoring the movement date/time 50563 corresponding tothe volume movement information (availability) ID “3” reads in the factthat the movement number 50562 is “3” and the movement date/time 50563is “(established date/time−creation date)×⅔”, and it acquires the value“high” for the movement destination availability characteristics 50564corresponding to same.

Thereupon, the CPU 5030 refers to the physical storage regioncharacteristics table 5048, and acquires a value of “1100” for thestorage device ID 50481 and a value of “1161” for the physical storageregion ID 50482 corresponding to the combination of a “low” entry in theperformance characteristics 50483 and a “high” entry in the availabilitycharacteristics 50484.

In a similar manner, the CPU 5030 sends a request for the logical volumehaving a logical volume ID “Volume 1” to be moved to the physicalstorage region corresponding to the storage device ID “1100” and thephysical storage region ID “1161”, to the high-end storage device 1000.

Thereby, the logical volume is moved in the high-end storage device1000, and in the mid-range storage device 1100, the physical storageregion ID 11463 corresponding to the logical volume ID 11461 value“Volume 3” in the logical/physical mapping table 1146 is changed to“1161”, and the address in physical storage region value is changed to“1024-2047”.

(Third Movement of Logical Volume “Volume 1”)

Next, the movement step 7053 in the logical volume movement illustratedin FIG. 2 will be described in detail.

With respect to the logical volume having a logical volume ID “Volume1”, at a time three days before the date and time in the establisheddate/time 50493, the CPU 5030 monitoring the movement date/time 50513corresponding to the volume movement information (performance) ID “3”reads in the fact that the movement number 50512 is “2” and the movementdate/time 50513 is “established date/time−3”, and it acquires the value“high” for the movement destination performance characteristics 50514corresponding to same.

Thereupon, the CPU 5030 refers to the physical storage regioncharacteristics table 5048, and acquires a value of “1000” for thestorage device ID 50481 and a value of “1061” for the physical storageregion ID 50482 corresponding to the combination of a “high” entry inthe performance characteristics 50483 and a “high” entry in theavailability characteristics 50484.

The CPU 5030 sends a request for the logical volume having a logicalvolume ID “Volume 1” to be moved to the physical storage regioncorresponding to the storage device ID “1000” and the physical storageregion ID “1061”, to the high-end storage device 1000, via themanagement I/F 5020 and the management I/F 1020.

When the storage device control section 1040 of the high-end storagedevice 1000 receives the movement request for the logical volume, theCPU 1041 processes the request in accordance with the volume movementprogram 1044.

The CPU 1041 refers to the external storage region flag table 1047 andthe external logical volume table 1048 in the memory 1045, and itacquires information indicating that the logical volume having a logicalvolume ID of “Volume 1” is the logical volume “Volume 3” of the externalstorage device “1100”.

Thereupon, the CPU 1041 recognizes that the storage device ID containedin the request is “1000”, and it acquires the data in the logical volume“Volume 3” from the mid-range storage device 1100 via the externalconnection I/F 1030 and the storage I/F 1110. The volume movement means1044 writes the acquired data to the address “0-1023” of the physicalstorage region 1061.

Thereupon, the CPU 1041 sets a value of “0” for the external storageregion flag 10472 corresponding to a logical volume ID 10471 of “Volume1” in the external storage region flag table 1047. Furthermore, the CPU1041 deletes the information corresponding to the logical volume ID10481 value “Volume 1” from the external logical volume table 1048.Thereupon, the CPU 1041 adds information to the logical/physical mappingtable 1046, indicating a logical volume ID 11461 of “Volume 1”, a paritygroup ID 10462 of “10462”, a physical storage region ID 10463 of “1061”and an address in physical storage region 10464 of “0-1023”.

(Fourth Movement of Logical Volume “Volume 1”)

Next, the movement step 7054 in the logical volume movement illustratedin FIG. 2 will be described in detail.

With respect to the logical volume having a logical volume ID “Volume1”, at a time one day after the date and time in the establisheddate/time 50493, the CPU 5030 monitoring the movement date/time 50513corresponding to the volume movement information (performance) ID “3”reads in the fact that the movement number 50512 is “3” and the movementdate/time 50513 is “established date/time+1”, and it acquires the value“low” for the movement destination performance characteristics 50514corresponding to same.

Moreover, in a simultaneous fashion, the CPU 5030 monitoring themovement date/time 50517 corresponding to the volume movementinformation (availability) ID of “3” reads in the fact that the movementnumber 50562 is “4” and that the movement date/time 50563 is“established date/time+1”, and it acquires the value “low” for themovement destination performance characteristics 50564 corresponding tothe same.

Thereupon, the CPU 5030 refers to the physical storage regioncharacteristics table 5048, and it acquires a value of “1100” for thestorage device ID 50481 and a value of “1163” for the physical storageregion ID 50482 corresponding to the combination of a “low” entry in theperformance characteristics 50483 and a “low” entry in the availabilitycharacteristics 50484.

In a similar manner, the CPU 5030 sends a request for the logical volumehaving a logical volume ID “Volume 1” to be moved to the physicalstorage region corresponding to the storage device ID “1100” and thephysical storage region ID “1163”, to the high-end storage device 1000.

The CPU 1041 of the high-end storage device 1000, upon receiving thismovement instruction, commands the mid-range storage device 1100 toperform movement of the logical volume. Thereupon, the CPU 1141 of themid-range storage device 1100, upon receiving this instruction, addsinformation to the logical/physical mapping table 1146, indicating alogical volume ID 11461 of “Volume 3”, a parity group ID 10462 of“1160”, a physical storage region ID of “1163” and an address inphysical storage region of “1024-2047”.

Thereupon, the CPU 1041 of the high-end storage device 1000 sets a valueof “1” for the external storage region flag 10472 corresponding to alogical volume ID 10471 of “Volume 1” in the external storage regionflag table 1047. It also adds information to the external logical volumetable 1048 indicating an logical volume ID 10481 of “Volume 1”, astorage device ID 10482 of “1100”, and an external logical volume ID10483 of “Volume 3”. Furthermore, information relating to the logicalvolume ID 10461 “Volume 1” is deleted from the logical/physical mappingtable 1046.

(Movement of Logical Volume “Volume 2”)

Logical volume movement is performed similarly for a logical volumehaving the logical volume ID “Volume 2”, also. FIG. 19 is a diagramillustrating the volume movement for Volume 2.

The logical volume 7100 is a logical volume identified by the logicalvolume ID “Volume 2” in the high-end storage device 1000. As shown inthe logical volume/data attribute table 5055 in FIG. 18, this is a maillog with an established date/time of 7/15; and, as shown in the dataattribute/change characteristics table 5054 in FIG. 16, thecorresponding value of the performance change characteristics ID 50542is “1” and that of the availability change characteristics ID 50543 is“2”.

More specifically, the volume movement information (performance) ID50511 in the volume movement information table (performance) 5051 inFIG. 12B, that is indicated by the volume movement information ID 50494in the performance change characteristics table 5049 in FIG. 12A, has avalue of “1”. Furthermore, the volume movement information(availability) ID 50561 in the volume movement information table(availability) 5056 in FIG. 14(B), that is indicated by the volumemovement information ID 50404 in the availability change characteristicstable 5050 in FIG. 14(A), has a value of “2”.

Consequently, the logical volume 7100 having a logical volume ID of“Volume 2” is moved in accordance with the volume movement information(performance) ID 50511 of “1” and the volume movement information(availability) ID 50561 of “2”.

The logical volume 7100 is assigned initially to a physical storageregion 1061 which has both high performance and high availability. Thisassignment can be instructed by the user, for example, or it may becarried out by moving the logical volume upon the first judgmentoperation after allocation, as in the case of “Volume 1”.

Subsequently, when one third of the time period from the time of firstassignment until the established date/time, “storage end date”, haselapsed, the logical volume 7100 is moved to the physical storage region1071 which has “medium” performance and “high” availability (movementstep 7151).

Thereupon, at the established date/time, “change storage conditions”,the logical volume 7100 is moved to the physical storage region 1073which has “medium” performance and “low” availability (movement step7152).

Thereupon, when two thirds of the time period from the time of firstassignment until the established date/time, “storage end date”, haselapsed, the logical volume 7100 is moved to the physical storage region1163 which has “low” performance and “low” availability (movement step7153).

The detailed processing carried out in the high-end storage device 1000and the mid-range storage device 1100 during movement of the logicalvolume is similar to that in the case of “Volume 1” described above, anda repeated description is therefore omitted here.

In the procedures for moving logical volumes as described above, thetiming at which to move a logical volume is calculated by the managementserver 5000 in the form of a specific date and time, by a calculatingfunction provided in the management server 5000, at prescribed timeintervals, on the basis of the movement date/time acquired from thevolume movement information table (performance) 5051 and the volumemovement information table (availability) 5056, the time thus calculatedis compared with the current time to determine whether a timing has beenreached at which a logical volume should be moved.

The method for monitoring and determining the movement timing is notlimited to this. For example, it is also possible to adopt the followingcomposition.

Firstly, when the performance characteristics table 5049 and theavailability characteristics table 5050 have been created, themanagement server 5000 calculates the absolute date and time of thetiming at which movement is to be carried out on the basis of themovement date/time 50513 in the volume movement information table(performance) 5051, and the movement date/time 50563 in the volumemovement information table (availability) 5056, and then it generates amovement schedule table 5057 as illustrated in FIG. 24. The movementschedule table 5057 comprises, for each logical volume, a data attributestored in that logical volume, the creation date thereof, theestablished date/time, the movement date/time storing the absolutedate/time for movement calculated from the volume movement informationtable (performance) 5051 and the volume movement information table(availability) 5056, and the performance and availability required ofthe destination physical storage region at the stated movementdate/time.

At prescribed time intervals, the CPU 5030 of the management server 5000determines whether or not a timing at which movement must be performedhas been reached, by comparing the movement date/times in the movementschedule table 5057 with its own internal clock.

Furthermore, in the present embodiment, relocation is achieved bycopying the data in a logical volume to an optimal storage region, inaccordance with the previously determined temporal change in performanceand availability for respective data attributes, but the invention isnot limited to this. For example, it is also possible to adopt acomposition wherein the characteristics of the actual physical storageregion in which the logical volume is located are changed to desiredcharacteristics, by means of back-up processing, replication processing,caching, or the like, as described above.

In many cases, the temporal change in the performance and availabilityrequired of the storage destination, by the data to be stored by theapplication server in a storage device in this way, is dividedpreviously according to the type of data. In the present embodiment,logical volumes are assigned to an optimal physical storage region atthe optimal timing on the basis of the characteristics of the data to bestored therein.

According to the present embodiment as described above, it is possibleto assign a logical volume to an optimal physical storage region, at anoptimal timing, in accordance with previously determined temporal changein the performance and availability required by the logical volume,depending on the type of data stored in the logical volume, withouthaving to monitor the actual access frequency and predict future accessoperations on the basis of these monitoring results.

If there are a plurality of high-end storage devices managed by themanagement server via the management I/F 5020, then the logical volumeID 50551 in the logical volume/data attribute table 5055 is anidentifier which identifies the high-end storage device and a logicalvolume within that high-end storage device.

Second Embodiment

Next, a second embodiment of the present invention will be described.

FIG. 20 is a block diagram of an information processing system accordingto the present embodiment.

As this diagram shows, the information processing device according tothe present embodiment comprises a high-end storage device 1000, amid-range storage device 1100, a disk array type back-up device 2000, atape library 2100, a switch 3000, an application server 4100, and a NAScontroller 5100.

The high-end storage device 1000 and the mid-range storage device 1100have similar compositions to those of the first embodiment, beingstorage devices for storing data used by the application server 4100.

The disk array type back-up device 2000 and the tape library 2100respectively have the same composition as those of the first embodiment,being storage devices for backing up the data stored in the high-endstorage device 1000 and the mid-range storage device 1100.

The NAS controller 5100 is a computer device providing network fileservices to the application server 4100. As shown in the diagram, theNAS controller 5100 comprises a storage I/F 5110 connected to a storageI/F 1010 of the high-end storage device 1000 and a storage I/F 1110 ofthe mid-range storage device 1100, via the switch 3000, a network I/F5125 connected to the application server 4100, and a management I/F 5120connected to the management I/F 1020 of the high-end storage device 1000and the mid-range storage device 1100.

The NAC controller 5100 has a file system for the data stored in thehigh-end storage device 1000 and the mid-range storage device 1100, andit provides network file services by using this file system. In thepresent embodiment, data is moved in file units by using this functionof the NAS controller 5100.

The application server 4100 is a computer device which executes anapplication program using data stored in the high-end storage device1000 and the mid-range storage device 1100. The application server 4000accesses the data stored in the high-end storage device 1000 and themid-range storage device 1100 by means of the network file serviceprovided by the NAS controller.

Similar information to that in the memory 5040 of the management server5000 in the first embodiment is held in the memory of the NAS controller5100.

In the present embodiment, however, since the data is moved in fileunits, the item name of the volume movement information ID 50494 in theperformance change characteristics table 5049 is a file movementinformation ID, and the item name of the volume movement information ID50504 in the availability change characteristics table 5050 is also afile movement information ID.

Furthermore, the name of the volume movement information table(performance) 5051 is a file movement information table (performance),and the name of the volume movement information table (availability)5056 is a file movement information table (availability). Moreover, theitem names in the volume movement information (performance) ID 50511 andthe volume movement information (availability) ID 50561 are,respectively, file movement information (performance) ID, and filemovement information (availability) ID.

A file attribute table 5055 a is provided instead of the logicalvolume/data attribute table 5055. The file attribute table 5055 acontains the item, file name 50551 a, instead of the logical volume ID50551 in the logical volume/data attribute table 5055, and the dataattribute of the data of the file is held as the data attribute 50552 a.

Moreover, in addition to this, a file system table 5156 is also held inthe memory of the NAS controller 5100. One example of the composition ofa file system table 5156 is shown in FIG. 23. As this diagram shows, thefile system table 5156 comprises a file name 51561, a storage device ID51562, a physical storage region ID 51563, and an address in physicalstorage region 51564.

The file name 51561 is an identifier for identifying a file. The storagedevice ID 51562 is an identifier for the storage device in which thedata of the file identified by the file name 51561 is located. Thephysical storage region ID 51563 is an identifier for the physicalstorage region ID in which the data of the file identified by the filename 51561 is located. The address in physical storage region 51564 isan address representing the position within the physical storage regionat which the data of the file identified by the file name 51561 islocated.

By means of this file system table 5156, the NAS controller 5100 is ableto identify the storage device and the physical storage region in whicheach file is stored.

An overview of the processing according to the present embodiment is nowdescribed with reference to FIG. 21 and FIG. 22. The file name 8040, thedata attribute 8010, and the performance change characteristics 8020 andavailability change characteristics 8030 required of the storagedestination by the file having the relevant data attribute will bedescribed, for instance, by taking the case illustrated in FIG. 21 as anexample. These correspond respectively to the data attribute 7010, theperformance change characteristics graph 7020, the availability changecharacteristics graph 7030 and the logical volume ID 7040 according tothe first embodiment.

FIG. 22 is a diagram showing how a file is moved between physicalstorage regions of the storage device, in accordance with the file, thedata attribute thereof, and the characteristics of the data attributeillustrated in FIG. 21. In this diagram, the file 8000, movement step8051, movement step 8052, movement step 8053, and movement step 8054 arerespectively equivalent to the logical volume 7000, movement step 7051,movement step 7052, movement step 7053 and movement step 7054 accordingto the first embodiment.

However, in the first embodiment, the volume movement was controlled inaccordance with a volume movement program 1044 of the high-end storagedevice 1000. In contrast, in the present embodiment, the NAS controller5100 has file movement means, and the file movement is controlled by thefile movement means of the NAS controller 5100.

In the first embodiment, when a volume has been moved, the CPU 1041rewrites the logical/physical mapping tables 1046, 1146, and the like,in the high-end storage device 1000 and the mid-range storage device1100 in accordance with the volume movement program 1044. However, inthe present embodiment, when a file has been moved, the file movementmeans of the NAS controller 5100 rewrites the file system table 5156 inthe NAS controller 5100.

Moreover, in the first embodiment, a logical volume allocation screen9000 is used when assigning the logical volumes, but in the presentembodiment, a similar “file creation screen” is used when creating thefiles. In the “file creation screen”, the “logical volume ID” displayelement in the logical volume allocation screen 9000 is replaced by a“file name” display element, and the logical volume ID box 9100 isreplaced by a file name box.

As described above, the NAS controller 5100 operates similarly to themanagement server 5000 in the first embodiment, and it manages the datain file units in such a manner that a file is located in an optimalphysical storage device in accordance with a change in the performanceand availability required by the data in that file.

According to the present embodiment as described above, it is possibleto assign data in file units to an optimal physical storage region, atan optimal timing, in accordance with a previously determined temporalchange in the performance and availability required by that data,depending on the type of data stored, without having to monitor theactual access frequency and to predict future access operations on thebasis of these monitoring results.

1. A computer system comprising: a plurality of storage systems having aplurality of disk units which are configured into a plurality ofphysical storage regions for storing data and a storage controller whichprovides data files to at least one of a plurality of external devicesvia a network; a plurality of host computers coupling to at least one ofthe storage systems via a network and accessing data files for using thedata, the data files being provided by at least one of the storagesystems; and a management computer coupling the host computers and thestorage systems via network, wherein said management computer checks aperiod between a present time and a predetermined time for data in afirst data file, the predetermined time being later than the presenttime and sends to the storage system, an instruction for migration ofthe data to a second data file from the first data file according to theperiod, wherein a property of the second data file is different fromthat of the first data file, and wherein the storage system migrates thedata responsive to the instruction.
 2. A management computer managing,via a network, a plurality of storage systems each including data files,and a plurality of host computers storing data in either of the datafiles, said management computer comprising: a network interface to becoupled to the network; a processor coupled to the network interface;and a memory coupled to the network interface, wherein the memory holdsproperty of the data files, and data property related to the data storedin a first data file, the data property including a predetermined timedefined according to data property, wherein the processor checks aperiod between a present time and the predetermined time which is laterthen the present time, and sends, to a storage system via a network, aninstruction of migrating data to a second data file from the first datafile according to the period, and wherein a property of the second datafile is different from that of the first data file.
 3. In a computersystem including a host computer, and a plurality of storage systemseach including a data file in which data for the host computer is to bestored, and a management computer coupled to the host computer and thestorage systems, a method for data management comprising the steps of:receiving a request for assigning a first data file for data used by thehost computer, a type of which data stored in the volume to be assigned,and a predetermined time for data; specifying a pattern of temporalchange corresponding to the received type of data and the received timeof related data; allocating the first data file to the host computer forstoring the data; and checking a period between a present time and apredetermined time for data in the first data file, wherein thepredetermined time is later than the present time and migrating data toa second data file from the first data file according to the period, andwherein a property of the second data file is different from that of thefirst data file.
 4. A method for data management according to claim 3,wherein a specified time at which data is finished to be stored in acomputer system.
 5. A method for data management according to claim 3,wherein a type of data is related to audit data and the predeterminedtime is a specified time at which data is to be audited.